Total Network Tools 2002

home *** CD-ROM | disk | FTP | other *** search

/ Total Network Tools 2002 / NextStepPublishing-TotalNetworkTools2002-Win95.iso / Archive / Online Timer / LogTime.exe / file0008.bin < prev next >

Wrap

Text File | 1999-11-04 | 13.5 KB | 414 lines

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN//3.2"> <html> <head> <title>Christopher Heng's LOGTIME Frequently Asked Questions</title>   </head> <BODY LINK="#0000FF" BGCOLOR="#FFFFFF" TEXT="#000000" VLINK="#0000A0"> <center> <table border=0 cellpadding=0 width="100%"> <tr><td> <center> <hr size=4> LOGTIME Frequently Asked Questions Common questions about LOGTIME and their answers. <hr size=4> </center> </td></tr> </table> </center> CONTENTS <ol> Supposed Or Real Bugs <li><a href="#ntstartup">How do I get LOGTIME to automatically start up when I log into Windows NT?</a> <li><a href="#optionbutton">I get an error message when I click the Options button. What should I do?</a> <li><a href="#autodetectfails">I am using a dialer from XXX Software Company on Windows 95 and LOGTIME is not able to automatically detect an Internet connection. What can I do?</a> <li><a href="#tapiver">I get error messages about requiring TAPI 1.4. What should I do?</a> Supported Platforms/Hardware <li><a href="#runin98">Does LOGTIME run on Windows 98?</a> <li><a href="#runinnt">Does LOGTIME run on Windows NT?</a> <li><a href="#isdn">Does LOGTIME work with my ISDN card/modem?</a> <li><a href="#adsl">Does LOGTIME work with my ADSL or cable modem connections?</a> Configuration Issues <li><a href="#prepaidcharge">I pay my ISP a flat monthly charge of $XX.XX and I get Y hours free access time every month. When I exceed that free time, I pay $Z.ZZ per hour or part thereof. How do I configure LOGTIME?</a> Miscellaneous Issues <li><a href="#editlog">Is there a way for me to edit the log file?</a> <li><a href="#currentsession">Is there a way for me to find out how long I have been connected to my ISP?</a> <li><a href="#reboot">What happens if I have to reboot in the middle of a Windows session, or if Windows crashes/hangs?</a> <li><a href="#latestversion">Can you inform me when a new version of LOGTIME is released?</a> <li><a href="#sources">Is the source code for LOGTIME available?</a> </ol> ANSWERS <dl> <dt><a name="ntstartup">How do I get LOGTIME to automatically start up when I log into Windows NT?</a> <dd> [Win32] Some early versions of LOGTIME did not automatically start up when you log into NT even when you configured it to do so. <a href="http://logtime.cjb.net/">Check out</a> the latest version to see if this has been fixed. If you really cannot get LOGTIME to automatically start monitoring everytime you log into NT, simply create a shortcut to LOGTIME in your Startup group, with the following command line: "c:\Program Files\LOGTIME\logtimew" -m where you should replace the "c:\Program Files\LOGTIME\" with the path where you installed LOGTIME. The argument "-m" is needed to make LOGTIME monitor your computer for Internet connections automatically. <dt><a name="optionbutton">I get an error message when I click the Options button. What should I do?</a> <dd> [Win32] You may have to update one of your Windows system components from Microsoft. <a href="http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp">Click here</a> to get your free update directly from Microsoft. I suggest you get the upgrade anyway. It might solve a lot of heartaches with many new programs being released (and perhaps even existing ones). The update is free. <dt><a name="autodetectfails">I am using a dialer from XXX Software Company on Windows 95 and LOGTIME is not able to automatically detect an Internet connection. What can I do?</a> <dd>[Win32] LOGTIME automatically detects a connection in one of two ways. The first way, available in version 2.0 and above, is to detect a modem connection made by a program using Windows Telephony. The second way, available only in 2.1 and above, is for it to detect Remote Access Service calls. If you are currently using one of these methods, and LOGTIME fails to detect the call, try the other method. If you do not know which method you are using, click Options | Monitor and check Type of Monitoring group. See the online manual for more information about what the various options mean. If both the methods fail, you can still resort to manual logging. Alternatively, if your dialer supports script files, you might want to consider using the dialer's scripting facility to launch LOGTIME to log a call when a connection is made. See the online manual on How to Start and Stop Logging a Connection for more information. If you are using an ADSL or a cable modem that accesses the Internet via a plug-in in your browser, see the question in this FAQ: <a href="#adsl">Does LOGTIME work with my ADSL connection?</a> <dt><a name="tapiver">I get error messages about requiring TAPI 1.4. What should I do?</a> <dd> [Win32] This error message should only occur in older versions of LOGTIME. It is due to an overzealous checking of all communications ports on LOGTIME's part (even when it was not monitoring those ports). You should <a href="http://logtime.cjb.net">upgrade</a> to the latest version. <dt><a name="runin98">Does LOGTIME run on Windows 98?</a> <dd>[Win32] Yes. <dt><a name="runinnt">Does LOGTIME run on Windows NT?</a> <dd>[Win32] Yes. <dt><a name="isdn">Does LOGTIME work with my ISDN card/modem?</a> <dd>[Win32] Users report that LOGTIME is able to automatically detect a connection made with ISDN cards/modems. <dt><a name="adsl">Does LOGTIME work with my ADSL or cable modem connections?</a> <dd>[Win32] If you are using an ADSL or a cable modem that accesses the Internet via a plug-in in your web browser, it is likely that the current version of LOGTIME will fail to automatically detect the connection. You can, however, still manually log the connection using LOGTIME. Support for automatically detecting such connections is in my TODO list for some future version. Disclaimer: no promises. <dt><a name="prepaidcharge">I pay my ISP a flat monthly charge of $XX.XX and I get Y hours free access time every month. When I exceed that free time, I pay $Z.ZZ per hour or part thereof. How do I configure LOGTIME?</a> <dd>[Win32][Win16][Linux] Your seconds per unit should be 3600 (60 seconds per minute multiplied by 60 minutes). Define Frame0 to have a charge of $Z.ZZ. Your prepaid charge should be Y multiplied by $Z.ZZ. The $XX.XX amount you pay your ISP should be entered into the "Monthly/weekly fee" box. <dt><a name="editlog">Is there a way for me to edit the log file?</a> <dd>[Win32][Linux] Usually this question is raised because someone only started using LOGTIME from the middle of the month, or he accidentally quit LOGTIME and forgot to clock some online time. There is no provision for a user to edit the log file from LOGTIME in the current version. However, there is a workaround to get LOGTIME to record your missing hours on the Internet. If you are using LOGTIME for Windows 95/98/NT, you may wish to do the following: <ol> <li>Doubleclick the LOGTIME icon. <li>Select the ISP that you wish to clock to. <li>Note the current time on the computer clock and click the BEGIN button. <li>Advance the computer clock by the number of hours, minutes, seconds that you want LOGTIME to record. <li>Click the END button. <li>Restore the computer clock to the correct time. </ol> <dt><a name="currentsession">Is there a way for me to find out how long I have been connected to my ISP?</a> <dd>[Win32] Move your mouse over the LOGTIME icon in the system tray. The name of the ISP to which you are currently connected and the duration of your call will be displayed in a tooltip. <dt><a name="reboot">What happens if I have to reboot in the middle of a Windows session, or if Windows crashes/hangs?</a> <dd>[Win32][Win16] One of the sad facts of life about running programs under Windows is that on occasion, you may find that some programs crash the system or cause Windows to hang, and you need to reboot the system to continue working. This is not a problem unless you are also connected to your ISP and have invoked LOGTIME to begin the timer. Rebooting when you have begun the timer without stopping the timer can cause your log results to be inaccurate. If you have LOGTIME 2.1b and above, the next time LOGTIME restarts, it will detect that you have crashed in the previous session and present you with a dialog box of the various actions you can take. Alternatively, you can also configure LOGTIME to automatically fix the error using the Options | Recovery property page. If you have a version earlier than 2.1b, you should immediately run LOGTIME after rebooting and click the End button on the main dialog window. The results of the interrupted session is likely to be somewhat inaccurate, depending on how long you took from the time Windows crashed (or hung or rebooted) and the time you ran LOGTIME to stop the timer. <dt><a name="latestversion">Can you inform me when a new version of LOGTIME is released?</a> <dd>[Win32][Win16][Linux] Join the <a href="http://logtime.cjb.net/mailing.html">LOGTIME Announcements mailing list</a>, which was created for precisely this purpose. <dt><a name="sources">Is the source code for LOGTIME available?</a> <dd>[Win32][Win16][Linux] Not currently. Please do not email me about this unless you are offering to pay for it. </dl> <hr> LOGTIME FAQ: Bundled Edition. Copyright © 1996-1999 by Christopher S L Heng. All rights reserved. </body> </html>